Re: Question about a NAME/TOKEN pair restriction
I would guess (without checking the code) that the restriction is because task termination cleanup of name/token pairs owned by the terminating task is done by a static system resource manager which runs before the dynamic resource managers established via RESMGR. Actually, it is the other way around. Name/Token resource managers are established via RESMGR. Dynamic resource managers established via RESMGR get control before static system resource managers. A system-created-via-RESMGR resource manager might or might not run before your RESMGR resource manager, so if you were to create a name/token in your RESMGR resource manager, and you were in a case where the name/token resource manager ran before, then your name/token would not be cleaned up properly. RESMGR resource managers run in LIFO order from the time of establishment. In specific cases (where you control all the flows) you might know the order in which they were established and thus know the order in which they will be given control. 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
Re: Question about a NAME/TOKEN pair restriction
That sounds logical. Thanks, Jim! Jerry On Thu, 27 Dec 2007 01:10:45 -0500, Jim Mulder [EMAIL PROTECTED] wrote: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU wrote on 12/26/2007 01:10:14 PM: For both the IEANTCR and IEANTRT name/token pair service macros, the documentation states: Restrictions --- Do not use the IEANTCR callable service in a RESMGR resource manager routine unless one of the following is true: - The resource manager is running for a daughter task of the task that owns the name/token pair. What is the definition of a daughter task? Is it only the immediate subtask of the current task or can it be a grand daughter or great great great grand daughter subtask as well? I believe this would be true for any descendant of the task which owns the name/token pair. I would guess (without checking the code) that the restriction is because task termination cleanup of name/token pairs owned by the terminating task is done by a static system resource manager which runs before the dynamic resource managers established via RESMGR. 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
Question about a NAME/TOKEN pair restriction
For both the IEANTCR and IEANTRT name/token pair service macros, the documentation states: Restrictions --- Do not use the IEANTCR callable service in a RESMGR resource manager routine unless one of the following is true: . . . - The resource manager is running for a daughter task of the task that owns the name/token pair. What is the definition of a daughter task? Is it only the immediate subtask of the current task or can it be a grand daughter or great great great grand daughter subtask as well? TIA, Jerry -- 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
Re: Question about a NAME/TOKEN pair restriction
IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU wrote on 12/26/2007 01:10:14 PM: For both the IEANTCR and IEANTRT name/token pair service macros, the documentation states: Restrictions --- Do not use the IEANTCR callable service in a RESMGR resource manager routine unless one of the following is true: - The resource manager is running for a daughter task of the task that owns the name/token pair. What is the definition of a daughter task? Is it only the immediate subtask of the current task or can it be a grand daughter or great great great grand daughter subtask as well? I believe this would be true for any descendant of the task which owns the name/token pair. I would guess (without checking the code) that the restriction is because task termination cleanup of name/token pairs owned by the terminating task is done by a static system resource manager which runs before the dynamic resource managers established via RESMGR. 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
