Storage Statistics are displayed using the D STOR and D STORXA commands.
When there are non-zero numbers in the "Failed" column, should there be any cause for concern or worry?
Release 5.2
TPX-Session Management-Access Management package
A failed request indicates that there was no space left in the slot pool that was requested so the request is "moved" to a larger slot pool. So it actually is not a failure as much as a sign that the particular pool is getting requests that need to be satisfied in a different pool.
This number is most important to Broadcom Support in debugging a U0032 ABEND since it will point to the problem area of the storage slots rather quickly.
In this example, Slots 10, 11, & 12 (below the line) show a number of failed requests in the "Failed" column. This is likely related to the Max Use of 100% that has been logged for these same slots. However since the current use for each is 0% and as long as there is no ABEND situation, these failed requests are no cause for alarm.
RDCTPX - GM2 ************* TPX Operator ********************** TEN0217 Storage Statistics (Below 16M line) Open ACBs: 0103 Total ACBs: 4829 Terminals: 0016 Applications: 0270 DSA Bytes: 04718592 Current Use: 013 % High Use: 017 % Free Areas:0005 Slot Bytes: 01568768 Current Use: 000 % High Use: 066 % Overflows:00162 Slot Size * Count = Bytes Curr.Use Max.Use Failed Requests 01 00008 2048 16384 000 % 002 % 0 187739 02 00016 1024 16384 000 % 024 % 0 3477813 03 00032 1024 32768 000 % 003 % 0 218542 04 00064 768 49152 007 % 009 % 0 106916 05 00128 384 49152 003 % 014 % 0 496536 06 00256 752 192512 000 % 002 % 0 4214641 07 00512 64 32768 001 % 065 % 0 169996 08 01024 48 49152 000 % 027 % 0 166688 09 02048 80 163840 000 % 056 % 0 1489297 10 04096 120 491520 000 % 100 % 323 4451498 11 08192 48 393216 000 % 100 % 202 870866 12 10240 8 81920 000 % 100 % 162 46 ******************************** BOTTOM OF DATA *****************************