IBM Mainframe Discussion List <[email protected]> wrote on 10/01/2006 09:56:08 PM:
> 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? Not that I am aware of. When IDENTIFY creates a minor CDE, I would think that it gets cleaned up when the corresponding major CDE gets cleaned up. > 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. Not that I am aware of. > 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? From the manual: "If an authorized caller creates an entry name for a module in the link pack area, the IDENTIFY service places an entry for the alias on the active link pack area queue. If an unauthorized caller creates an entry name for a module in the link pack area, the IDENTIFY service places an entry for the alias on the task's job pack queue." I would think that job pack queue CDEs go away when the jobstep TCB terminates, and active LPA CDEs go away when the system is reIPLed. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY ---------------------------------------------------------------------- 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
