If your IDENTIFY was for a module originally loaded from LPA, then I don't think DELETE cleans everything up, otherwise I agree with Shmuel, et al that DELETE is the un-IDENTIFY.
On 10/6/06, Charles Mills <[EMAIL PROTECTED]> wrote:
Shmuel, I still think you have this wrong. Let's assume that no such entry point as ZZZ exists anywhere on our system, okay? I issue a LOAD EP=ZZZ and it fails. This is my initial condition. This is the condition in which our hypothetical process starts and to which it should return if it wishes to leave things as it found them. It issues an IDENTIFY EP=ZZZ. Now LOAD (and DELETE) EP=ZZZ succeed. What macro could the program issue now to get back to its original state, the one in which ZZZ did not exist? Not DELETE. No matter how many DELETEs I issue for ZZZ, a LOAD EP=ZZZ will still succeed. So the question remains, what is the un-IDENTIFY function? Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Shmuel Metz (Seymour J.) Sent: Thursday, October 05, 2006 4:29 PM To: [email protected] Subject: Re: IDENTIFY questions In <[EMAIL PROTECTED]>, on 10/05/2006 at 07:01 AM, Charles Mills <[EMAIL PROTECTED]> said: >I don't think so. DELETE is the opposite of LOAD, IDENTIFY is analogous to LOAD. >DELETE decrements the use count Water is wet. >it does not "destroy" a created entry point, does it? It does if the use count goes to zero. ---------------------------------------------------------------------- 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
