Troubleshooting
Problem
This document describes message CPI0999.
Resolving The Problem
The following document contains information regarding msgCPI0999 - Storage directory threshold reached.
The CPI0999 message means the static directory is filling up, the disk extents are getting too small, or the partition is fragmented. The temporary directory and static directory only get reset during an IPL.
While having the most current PTFs applied is highly recommended, this condition is most often seen when the system has nearly run out of space, yet storage levels may be back to the normal usage level when noticed. In a near out of storage condition, a CPF0907 would typically be present from some time near the first CPI0999. Use DSPLOG to verify.
If there is no CPF0907 near the date and timeframe of the CPI0999, it may indicate fragmentation. This can often be due to application changes or workload changes. To correct the fragmentation, the STRDSKRGZ command should be run.
The CPI0999 message means the static directory is filling up, the disk extents are getting too small, or the partition is fragmented. The temporary directory and static directory only get reset during an IPL.
While having the most current PTFs applied is highly recommended, this condition is most often seen when the system has nearly run out of space, yet storage levels may be back to the normal usage level when noticed. In a near out of storage condition, a CPF0907 would typically be present from some time near the first CPI0999. Use DSPLOG to verify.
If there is no CPF0907 near the date and timeframe of the CPI0999, it may indicate fragmentation. This can often be due to application changes or workload changes. To correct the fragmentation, the STRDSKRGZ command should be run.
*Note: The STRDSKRGZ by default will not reorg SSD drives. This is to preserve the SSD life. An occasional reorg is not a concern, but a weekly reorg would more drastically decrease the SSD drive lifespan. If you have SSD and need to STRDSKRGZ, then you will need the following PTF applied:
7.2 MF66947 (Included on Cumulative C0114720)
7.3 MF66962 (Included on Cumulative C0128730)
7.4 MF66964 (Included on Cumulative C0121740)
7.3 MF66962 (Included on Cumulative C0128730)
7.4 MF66964 (Included on Cumulative C0121740)
Which will provide the following macros:
smsetdefragssd [SSD will be included in the defragmentation]
smresetdefragssd [Reset to Default. SSD will not be included in the defragmentation]
smgetdefragssd [Display if SSD will be included or will not be included in the defragmentation]
smresetdefragssd [Reset to Default. SSD will not be included in the defragmentation]
smgetdefragssd [Display if SSD will be included or will not be included in the defragmentation]
1. STRSST and sign in
2. Option 1. Start a service tool
3. Option 4. Display/Alter/Dump
4. Option 1. Display/Alter storage
5. Option 2. Licensed Internal Code (LIC) data
6. Option 14. Advanced analysis
7. Enter a 1=Select on the top blank line for the Option and smgetdefragssd for the Command, then press Enter
8. [leave Options blank] and press enter
9. If you have SSD and they are not included, then follow the above steps but using the macro command smsetdefragssd [leave the options blank]
*Note: This setting will persist through an IPL but will NOT survive an upgrade or potentially future code updates. For this reason, always check the smgetdefragssd before running a disk reorg if you have SSD drives.
In addition, the SST advanced analysis macro DUMPSTATDIR should run to check if the system is running out of directory entries, and Directory dumps (DIRDUMP) may be needed to attempt in determining the cause.
Running the DIRDUMP is preferably done through QMGTOOLS under the Internals area, Temp Storage menu, Directory dump menu, Start Directory dump: QMGTOOLS: Temp Storage menu
http://www-01.ibm.com/support/docview.wss?uid=nas8N1020142
Performance Explorer (PEX) data may be required if the DIRDUMP does not provide the answer for the cause.
An IPL will often clear the condition, however, not explain why the CPI0999 was encountered or prevent future occurrences. Thus, why the data collected in advance is critical to determine the cause.
If a Main Storage Dump (MSD) occurs, it is recommended to capture it for attempt at determining the root cause.
Once the CPI0999 begins, it continues to be signaled every hour until an IPL is performed. Otherwise, if the the CPI0999 is understood and can be accepted (i.e. Prior storage condition from near the same date/time, has been corrected and understood), a specific data area can be created to stop the message from being issued. Refer to document N1012739, Turning off Message CPI0999. https://www.ibm.com/support/pages/turning-message-cpi0999
Contact your IBM i software service provider for assistance. Please use the IBM i Support MustGather tools to run a Directory Threshold collection by either using command QMGTOOLS/DIRTHRCOL, or from the QMGTOOLS Internals menu (see https://www.ibm.com/support/pages/node/645327).
Running the DIRDUMP is preferably done through QMGTOOLS under the Internals area, Temp Storage menu, Directory dump menu, Start Directory dump: QMGTOOLS: Temp Storage menu
http://www-01.ibm.com/support/docview.wss?uid=nas8N1020142
Performance Explorer (PEX) data may be required if the DIRDUMP does not provide the answer for the cause.
An IPL will often clear the condition, however, not explain why the CPI0999 was encountered or prevent future occurrences. Thus, why the data collected in advance is critical to determine the cause.
If a Main Storage Dump (MSD) occurs, it is recommended to capture it for attempt at determining the root cause.
Once the CPI0999 begins, it continues to be signaled every hour until an IPL is performed. Otherwise, if the the CPI0999 is understood and can be accepted (i.e. Prior storage condition from near the same date/time, has been corrected and understood), a specific data area can be created to stop the message from being issued. Refer to document N1012739, Turning off Message CPI0999. https://www.ibm.com/support/pages/turning-message-cpi0999
Contact your IBM i software service provider for assistance. Please use the IBM i Support MustGather tools to run a Directory Threshold collection by either using command QMGTOOLS/DIRTHRCOL, or from the QMGTOOLS Internals menu (see https://www.ibm.com/support/pages/node/645327).
[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"6.1.0"}]
Historical Number
23581844
Was this topic helpful?
Document Information
Modified date:
31 May 2022
UID
nas8N1019460