Running the RB chain of an inactive TCB
Can someone explain to me the apparent contradiction in the following two pieces of information ? From the serialization section of SYS1.MACLIB(IHARB): If the task is not running and the local lock is held, the RB chain will not change. From APAR PQ81630: PQ76702 introduced code for MVSTCB TCB statistics. DFHDSMT calls DFHDSAUT for these statistics in routine CREATE_SNAPSHOT. DFHDSAUT will loop in routine TCB_SCAN due to not serializing the RB chain. A MVS local lock is not enough to serialize the RB chain. Thanks in advance, Mark. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Running the RB chain of an inactive TCB
On 1/17/2013 11:12 AM, Mark Henderson wrote: Can someone explain to me the apparent contradiction in the following two pieces of information ? From the serialization section of SYS1.MACLIB(IHARB): If the task is not running and the local lock is held, the RB chain will not change. From APAR PQ81630: PQ76702 introduced code for MVSTCB TCB statistics. DFHDSMT calls DFHDSAUT for these statistics in routine CREATE_SNAPSHOT. DFHDSAUT will loop in routine TCB_SCAN due to not serializing the RB chain. A MVS local lock is not enough to serialize the RB chain. When begs the question: if local lock is not enough, what serialization should be used? ;) More than likely the RB chain of a dispatchable TCB can be 100% safely traversed only while running in that TCB. -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Running the RB chain of an inactive TCB
From the serialization section of SYS1.MACLIB(IHARB): If the task is not running and the local lock is held, the RB chain will not change. From APAR PQ81630: PQ76702 introduced code for MVSTCB TCB statistics. DFHDSMT calls DFHDSAUT for these statistics in routine CREATE_SNAPSHOT. DFHDSAUT will loop in routine TCB_SCAN due to not serializing the RB chain. A MVS local lock is not enough to serialize the RB chain. When begs the question: if local lock is not enough, what serialization should be used? ;) More than likely the RB chain of a dispatchable TCB can be 100% safely traversed only while running in that TCB. That is correct. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Running the RB chain of an inactive TCB
In 50f87d72.5020...@phoenixsoftware.com, on 01/17/2013 at 02:38 PM, Edward Jaffe edja...@phoenixsoftware.com said: When begs the question: if local lock is not enough, what serialization should be used? ;) Dispatcher lock plus testing that the TCB is not dispatched? -- Shmuel (Seymour J.) Metz, SysProg and JOAT Atid/2http://patriot.net/~shmuel We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
