1. Is there an "un-IDENTIFY"? Following the principle of "you allocated it, you unallocate it," how do you "clean up" when you are done with the entry point created by IDENTIFY?
Answer: No to the first question. It will get cleaned up when you DELETE the entry point within which the identify'd entry resides. 2. Is there a macro or service that does what IDENTIFY does but with more control and/or options? Specifically, I would like to be able to create an entry point that was *not* marked as reentrant. Answer: No, unless you consider the binder -- adding an alias 3. If a program is present in the LPA, is executed in a batch job, and does an IDENTIFY, when does the IDENTIFY entry point go away? When the program or task that issued the IDENTIFY ends? At the end of the jobstep? Does it matter if the program is authorized? Answer: The location of the program doing the identify is irrelevant in all cases. The location of the entry being identified (LPA vs private) affects various things (and in the LPA case authorization matters). For example, if the program is authorized and the identified entry point is within LPA, then an active LPA CDE is created and that will never go away on its own. If you are not authorized, then a CDE is created within your private storage. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- 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
