Question & Answer
Question
I have some CICS Transaction Server for z/OS (CICS TS) performance reports that show very high GVUPWAIT counts and times. What might be causing these high counts and times and how do I determine the source of the GVUPWAIT?
Answer
The GVUPWAIT time DFHTASK field 184 is collected when various CICS domains need to periodically give up control to allow other tasks to run. In addition to the EXEC CICS commands described under the GVUPWAIT time where an application chooses to give up control to CICS, other CICS domains will give up control to avoid a runaway situation. This is typically seen for tasks that are browsing resources, such as:
files by the file control domain
terminals
functions where CICS domains browse the CICS catalog
RDO checking
and many other internal areas within CICS where it is desirable to give up control to allow other tasks an opportunity to run.
A CICS domain issues a DFHDSATM FUNCTION(CHANGE_PRIORITY) which results in the DFHTASK 184 GVUPWAIT monitor field count and time being incremented.
Product Synonym
CICSPA CICS PA;CICS/TS CICSTS CICS TS CICS Transaction Server
Was this topic helpful?
Document Information
Modified date:
24 August 2016
UID
dwa1295439