AS400 Suddenly Out Of Space
I have an AS400 V5R1 that was at 60% and now over the weekend shot up to 99 % full. I have no ideas why I lost all the space. This happend last week as well and I removed an old library but still happening. Reclaim Storage and Splfiles Does Nothing. Is there a Journal that could have gone nuts ?? The system does not tell me anything, just out of space. This happend after weekly IPL on weekend. Please Help. Thank you
Software/Hardware used:
Software/Hardware used:
ASKED:
November 17, 2009 1:58 AM
UPDATED:
November 17, 2009 10:02 PM
Answer Wiki:
You need to run a RTVDSKINF job then PRTDSKINF to view the disk space usage on your system.
This can run several hours though so run during downtime.
In the interim, do you schedule a cleanup job? CHGCLNUP F4 to view. If you haven't then you can use this to cleanup your history logs, etc..
Or WRKOBJ OBJ(QSYS/QHST*) OBJTYPE(*FILE) to manually delete QHST files
Check the QRPLOBJ library, you can clear this library.
If you know your system, type wrkobj *all/*all *jrnrcv. Delete the excessive jrnrcvs.
WRKOBJPDM for a specific library and sort by object size or DSPLIB and print out to see the large objects.
===============================================================
RTVDSKINF/PRTDSKINF might be no help if you have no prior baseline or trend data. Further, it might be the cause of hitting the limit if you run it. RCLSTG should be avoided if you don't know the cause -- it won't tell you anything.
V5R1?? or V6R1?
Sign on as an *ALLOBJ/*SPLCTL/*JOBCTL user at least.
Start a session and run WRKACTJOB. Press <F11> to view elapsed data. Place the cursor over in the column labeled AuxIO and press <F16> to sort. Start investigating the jobs from the top of the list on down. Press <F5> a couple times over the following couple of minutes to view refreshed statistics.
In a second session, run WRKOUTQ. (The default should be *ALL and you should have authority.) View the list to see if any *outq is receiving a high number of entries. Press <F5> to see if the number rises for any queue. Investigate suspicious *outqs to see what is being added.
I'd be suspicious of (1) journal receivers, (2) spooled files, (3) QRPLOBJ from a looping job and (4) streamfiles -- it _might_ be a shared directory that's getting added to. (RTVDIRINF/PRTDIRINF might be more appropriate than xxxDSKINF, but might also put you over the limit.)
If this is V6R1, it _might_ not be one of your jobs. If V6R1, is this a Power6 processor?
Tom
To see all answers submitted to the Answer Wiki: View Answer History.
Theer are a number of reasons for disk space getting gobbled up.
Firstly run the RTVDSKINF and PRTDSKINF to look for libraries or folders that seem to be larger than they should be.
depending on the size(disk) of your system, a simple thing like reports take up a lot of space. You will need to clean up old spool files and then either IPL the system or run the spool file clean up commands to free up the space the spool files used. The space a spool file uses is not made available immediately after the spool file is deleted.
If you are journaling, the journals will take up a lot of space.
The IFS also uses a lot of disk space. The IFS can be very difficult to analyze as you will have to drill down through the folders to see the contents.
If you do not IPL regularly and you compile often, old versions of the programs are stored in QRPLOBJ. QRPLOBJ is cleared only when the system IPL’s. You can clear it using CLRLIB QRPLOBJ.
Also check your history logs. QHST*. These build daily and may not be deleted. If you are using the OS/400 assistant, it will schedule a daily clean up based on the parameters you define. Do a GO CLEANUP and check the settings. Set them if it is not in use.
Email is another issue. If you are using the email servewr on the system, you may have rogue messages building up or a problem with 1 or more messages creating error logs. These are difficult to find. I had this problem and had to shut down my email server.
Lastly, you should do a RCLSTG. You may have to change your QSYSOPR message queue to hold messages and not break. The RCLSTG runs interactively and the breaking of the message will stop the reclaim process until the message is responded to.
Darryl Freinkel