Displaying IBM Session Manager storage management statistics
See:
To display IBM Session Manager storage statistics
Note: Normally, this diagnostic facility should be used only at the request of your local support representative and if GFS is active; by default, you can use this facility only if you have a security authorization level of 9.
From System view for a node, complete these steps:
- Select the Storage tab.
- If required, use the vertical scroll bar to reposition the 'frame' so that the Storage section is visible.
- If the Storage section is collapsed then to expand it, click its heading.
Statistics on dynamic storage use in various categories will be displayed; the (User) command that runs on the mainframe is QUERY STORUSE.
To display IBM Session Manager subpool statistics
Note: Normally, this diagnostic facility should be used only at the request of your local support representative and if GFS is active; by default, you can use this facility only if you have a security authorization level of 9.
From System view for a node, complete these steps:
- Select the Storage tab.
- If required, use the vertical scroll bar to reposition the 'frame' so that the Subpools section is visible.
- If the Subpools section is collapsed then to expand it, click its heading.
Statistics on subpool use (Name, Current size, Maximum size, When reached) will be displayed; the (User) command that runs on the mainframe is QUERY STORUSE POOL.
To display GFS statistics
Note: Normally, this diagnostic facility should be used only at the request of your local support representative and if GFS is active; by default, you can use this facility only if you have a security authorization level of 9.
From System view for a node, complete these steps:
- Select the Storage tab.
- If required, use the vertical scroll bar to reposition the 'frame' so that the GFS section is visible.
- If the GFS section is collapsed then to expand it, click its heading.
Statistics on the operation of GFS in your site's operating environment will be displayed - see Storage, Usage, and Stats.
Storage
The top GFS section displays the layout of storage managed by GFS - that is, the address and length of the storage and bitmaps used by GFS.
Field
|
Description
|
Maxstor
|
Indicates whether or not MAXSTOR processing is being used. Possible values are Yes or No.
|
Maptype
|
Shows whether GFS is using BIT maps or BYTE maps to manage storage.
|
Cushion
Address/Length
|
In all systems except z/OS, GFS ensures that a cushion of storage is retained outside of GFS control. This shows the address and length (in bytes) of that cushion.
|
Bitmap
Address/Length
|
Address and length (in bytes) of the bitmap table governing GFS controlled storage. The storage governed is above or below the line as indicated.
|
Storage
Address/Length
|
Address and length (in bytes) of the storage managed by GFS.
|
Usage
The GFS Usage section displays the amount of storage managed by GFS and the percentage of free storage available for various lengths of GET requests.
Note: GET requests are rounded up to the next 8-byte boundary.
Field
|
Description
|
Id
|
GFS manages storage in up to eight different submaps depending on the length of storage requested.
|
From/
To
|
Range of storage requests (in bytes) covered by this submap.
|
Bytes Managed
|
Length of storage (in bytes) governed by this submap.
|
Bytes Used
|
Number of 'Bytes Managed' actually allocated.
|
Bytes Free
|
Number of 'Bytes Managed' that are still available.
|
% Free
|
'Bytes Free' expressed as a percentage of 'Bytes Managed'.
|
SMAPS
|
Shows how the storage to be governed by each submap was defined at startup time. If only seven maps are described in this definition then the eighth map takes whatever storage remains.
|
Stats
The GFS Stats section displays statistics about the number of GET requests handled by GFS and their relative success.
Note: GET requests are rounded up to the next 8-byte boundary.
Field
|
Description
|
From/
To
|
Ranges shown are broken down according to the length of storage requested. These columns show the range of GET requests (in bytes) covered by the entry.
|
Number of GETs
|
Number of GET requests performed which fall within this length range.
|
First slot
|
Number of GET requests performed in this length range which have been satisfied by the first free storage element found.
|
All slots full
|
GET request was not successful in the first instance because the GFS submap, which would normally be used to satisfy this storage request, has insufficient storage left. The storage has been allocated in a different submap. A high figure in this column denotes either that the IBM Session Manager machine is running out of storage or that there is a logic error in IBM Session Manager whereby storage is not being freed.
|
Slot too small
|
GET request was not successful in the first instance because a free storage element has been found, but it is insufficient to satisfy this storage request. A high figure in this column (relative to the number of GET requests issued) may indicate a fragmentation problem. A Submap full condition will make this problem worse.
|
Parent topic: