X hits on this document

941 views

0 shares

0 downloads

0 comments

204 / 236

MVS Waits

The reason why the IMS control region can stand so little paging is that when one ITASK page faults in the CTL region, all ITASKs running in the CTL region halt.

CTL EXT Priv Page

This execution state is the same as the CTL Private Page execution state, except that the private page MVS referenced is located in the control regions extended private area, which is located above the 16 megabyte addressing line.

DEP Private Page

The thread was waiting for the resolution of a page fault for a page within its private area.

DEP EXT Priv Page

This execution state is the same as the DEP Private Page execution state, except that the private page MVS referenced is located in the regions extended private area, above the 16 megabyte addressing line.

LPA Page

The collector found the threads execution blocked for one of two reasons:

The application program (most likely compiler runtime routines copied to LPA or some IMS module running as a subroutine of the application program) was waiting for the resolution of a page fault for a page in the pageable link pack area (PLPA).

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

ELPA Page

The collector found the threads execution blocked for one of two reasons:

The application program (most likely compiler runtime routines copied to LPA or some IMS module running as a subroutine of the application program) was waiting for the resolution of a page fault for a page in the extended pageable link pack area (EPLPA).

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

204

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

Document info
Document views941
Page views941
Page last viewedWed Dec 07 19:43:26 UTC 2016
Pages236
Paragraphs8116
Words69808

Comments