Select sys_dname, jrnname, JOURNAL_ASPGRP, SIZJRNRCVĪfter deleting documents and folders, do the following:ĭelete any License Program Products (LPPs) that are not needed (if unsure, save the LPP to tape, and then delete). Via SQL: With current PTF levels at least V5R4x and up, to get a list of storage for all journal receivers for a journal on the system. If data replication over remote journaling is being used, do not delete the journal receiver in the HA solution. Print disk space informationĬ) Check the top to verify date/time the collection was taken, if not current, collect one: į) That generates a report, enter WRKSBMJOB, the spooled file is named QPRTOBJRPTĪt the top of the report, it shows the journal receiver consuming the most storage. To get the information on journal receivers:ī) Option 2. If SAVED or ON-LINE, they may be possibilities to delete.įollow the GO DISKTASKS report from this link: Select Option 5 to display and check the status. If they are large, on the operating system command line type the following: To delete journal receivers, on the operating system command line type the following: To clear any user libraries that are not needed, on the operating system command line type the following: To clear any job queues that are not needed, on the operating system command line type the following: To clear QEZJOBLOG and QEZDEBUG output queues (if not needed to debug storage growth or other open problems), on the operating system command line type the following: Then, verify the Number of days to keep objects is within reason. Verify that Allow cleanup is set to *YES. To verify CLEANUP is running, type the following: To delete old history files (except the most recent one), on the operating system command line type the following: In addition, some commands may not be available at all releases. Also note that any of the following can consume the remaining amount of space without warning. Some of these functions will delete, clear, or destroy data that may be unrecoverable. They are common ways to reduce storage used. Some of these functions may be long-running. The first portion includes tips to reduce Permanent Space allocated the second part shows areas to reduce Temporary Space allocated.Ĭaution: All of the following actions should be taken with caution and at the customer's discretion. This document is divided into two categories. For more information on DISKTASKS, refer to the following Technote, Go Disktasks Overview. Note: The collection may take up to several hours to complete. At least 3% free space is suggested to generate the output.

It shows the allocation of disk space across the system. If permanent storage growth, a DISKTASKS report is recommended. The percentage of system ASP used is high. IBM i technotes referenced in this document:Īn example of a system running at a high percentage of system ASP used is shown below.

Clean space system