>Here is the scenario... > >PROGRAM1 is in LPA (actually, dynamically added to the MLPA in this case >during testing, but it the sequence also fails if it is in LPA) and is marked >as >"RF RN RU", amode31, rmode any. The following sequence is executed by an >unauthorized, key 8 program... > >1. LOAD EP=PROGRAM1 This works correctly. > >2. IDENTIFY EP=PROGRAMA,ENTRY=(entry point returned from LOAD) This works. > >3. ATTACH EP=PROGRAMA This works. A subtask is attached and PROGRAM1 runs. > >If I use XDC at this point to display the TCB's (L TASKS), it shows a >subtask named PROGRAMA, which is what I expected. > >4. PROGRAMA is subsequently detached correctly. XDC says the subtask is gone. > >5. LOAD EP=PROGRAM1 Again, this works correctly. Same entry point >returned. > >6. IDENTIFY EP=PROGRAMA,ENTRY=(entry point returned from LOAD) This fails >with R15=8. >
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. Keith E. Moe Laid Back Software, Inc. http://www.laidbacksoftware.com [EMAIL PROTECTED] (408) 749-0655 (voice and FAX) (408) 480-2067 (cell) "We take our clients seriously, not ourselves." ---------------------------------------------------------------------- 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
