The data structure kc_pagepool_str is defined for the parameter type KC_PAGEPOOL. In the case of KC_GET_OBJECT, UTM returns information on the current utilization of the page pool in kc_pagepool_str.
Data structure kc_pagepool_str |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The fields in the data structure have the following meanings:
total_pages
Total number of pages in the page pool.
free_pages
Number of free pages.
gssb_pages
Number of pages which are utilized for GSSBs.
lssb_pages
Number of pages which are utilized for LSSBs.
tls_pages
Number of pages which are utilized for TLS areas.
uls_pages
Number of pages which are utilized for ULS areas.
dial_conv_pages
Number of pages which are utilized for service contexts by users.
tacclass_pages
Number of pages which are utilized for dialog input messages, and which are temporarily stored in TAC Class Queues.
fpmm_pages
Number of pages which are required for managing asynchronous messages.
fput_pages
Number of pages which are utilized for asynchronous messages.
msgtac_pages
Number of pages which are utilized for MSGTAC messages.
lput_pages
Number of pages which are utilized for temporarily stored LPUT records.
phys_msg_pages
Number of pages which are utilized for output messages and which need to be temporarily stored because they can only be transferred to the transport system in sections owing to their length.
reset_msg_pages
Number of pages which are utilized for reset messages.
log_rec_pages
Number of pages which are utilized for OSI TP log records.
other_pages
Number of other utilized pages.
In the case of UTM cluster applications, GSSB and ULS areas are stored in the global page pool of the UTM cluster application. As KC_PAGEPOOL only displays the utilization of the local page pool, the values for gssb_pages and uls_pages are always zero in UTM cluster applications.