X hits on this document

898 views

0 shares

0 downloads

0 comments

206 / 236

MVS Waits

CSA Page (GFA)

The collector found the thread active with its execution blocked for one of two reasons:

The application programor, more likely, some IMS module running as a subroutine of the application programwas waiting for the resolution of a page fault for a page in the common service area (CSA).

The thread had ISWITCHed to the IMS control region. While there, the collector found its ITASK waiting for the resolution of a page fault it took in CSA, or waiting to use the CPU behind another ITASK which had serialized the CTL Task by taking a page fault in CSA.

In either case, the page fault occurred at a time when the available frame queue (AFQ) was empty, so the request for the resolution of the page fault had to be put on the general frame allocation (GFA) queue, and that is where the collector found it.

Refer to the discussion of GFA under See CTL Private Page (GFA)on page 205.

LPA Page (GFA)

The collector found the thread with its execution blocked for one of two reasons:

The application programor, more likely, some IMS module running as a subroutine of the application programwas waiting for the resolution of a page fault for a page in the pageable link pack area (PLPA).

The thread had ISWITCHed to the IMS control region. While there, the collector found its ITASK waiting for the resolution of a page fault it took in LPA, or waiting to use the CPU behind another ITASK which had serialized the CTL task by taking a page fault in LPA.

In either case, the page fault occurred at a time when the available frame queue (AFQ) was empty, so the request for the resolution of the page fault had to be put in the general frame allocation (GFA) queue, and that is where the collector found it.

Refer to the discussion of GFA under See CTL Private Page (GFA)on page 205.

X-MEM Page (GFA)

The collector found the thread active. The IMS system was running with LSO=X or LSO=S. The thread issued a DL/I call, which was being processed by IMS modules running in the control region or DLISAS, but under the ASCB/TCB of the thread using MVS Cross Memory Services. DL/I processing took a page fault for a page in the control regions private area. The collector found the request for resolution of the page fault on the GFA queue, indicating that it occurred when the AFQ was empty.

206

OMEGAMON II for DBCTL Historical Component (EPILOG) Reference Manual Version 510

Document info
Document views898
Page views898
Page last viewedMon Dec 05 14:52:54 UTC 2016
Pages236
Paragraphs8116
Words69808

Comments