You could try to directly change the dispatching priority of a TCB with CHAP: https://www.ibm.com/docs/en/zos/2.5.0?topic=hsp-chap-change-dispatching-priority
My understanding is that after changing the dispatching priority for your task, the dispatcher will get control and (if you downgraded your TCB's priority) select another task to be run. Caveat: I don't know enough of the inner workings of z/OS, maybe IBM can shed some light here... -----Ursprüngliche Nachricht----- Von: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> Im Auftrag von Thomas David Rivers Gesendet: Dienstag, 7. Mai 2024 04:34 An: IBM-MAIN@LISTSERV.UA.EDU Betreff: [IBM-MAIN] Control dispatcher time-slice? We've got a test (with pthread-created TCBs) that we'd like to really have dispatched with tiny time slices so we can make sure things are working correctly... But - it seems that all of our time slices are "big" so we don't get the conflicts we'd like to exercise. Is there a way to tell the dispatcher to switch more quickly between TCBs - so we can get more radical multi-tasking? This is on a zPDT system (L01) with only one "physical" CPU... so we need the dispatcher to perhaps act in an atypical way for this exercise. Right now, we're seeing very little multi-tasking between our TCBs. - Thanks - - Dave R. - -- riv...@dignus.com Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
