Thanks for the responses. Keith...the thing is that I never do a DELETE on any of the modules. That's why I had coded for the RC=4 from IDENTIFY. It's the RC=8 when the module is in LPA that's bothering me. hal9001...I agree there are several workarounds I can do to get around this problem. It is a little more difficult in that I'm in a CICS region, the module could have already been loaded by another product (it's a "general purpose" CICS-supplied program), and it's occurring during start/shutdown/restart processing of a product where a lot of stuff goes away during shutdown processing. Even still, there are a number of ways I can get beyond this. What it boils down to is that I just want to know why the second (and subsequent) IDENTIFY gives a RC=4 if the loaded module previously came from STEPLIB and a RC=8 if the loaded module previously came from the LPA. Remember that in both scenarios, the entry point address for the second IDENTIFY is always the same as was used on the first IDENTIFY and the processing is always being done by an unauthorized program. Thanks, Ira W. Broussard In a message dated 1/26/2006 1:01:38 A.M. Central Standard Time, [EMAIL PROTECTED] writes:
At 21:46 -0800 on 01/25/2006, Keith E. Moe wrote about Identify Macro: >The problem is that programs "created" via IDENTIFY cannot be >deleted or otherwise made to disappear until task (I think) >termination. Even >if the module that it is identified against is deleted, the IDENTIFY >Entry Point remains. > >I had somewhat the same problem in that I had a Job Step program >that I used IDENTIFY against to create an alternate entry point for a >subtask attach. Because there was the possibility of attaching the >subtask multiple times, I wanted to IDENTIFY, ATTACH, DETACH, and >DELETE, making the subtask processing independent of the first >versus subsequent times. But you can't DELETE an IDENTIFY entry >point. I assume that when your main program starts up it does some one time housekeeping (setting up a Save Area or saving to the Linkage Stack, etc) before it gets into the main processing code. Why not do the LOAD there and save the entry address there and in the main loop just load the entry address and use it for the ATTACH? That way all the ATTACHs are the same since the LOAD is not in the processing loop. ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
