asp usage to 90%.. how can i check and bring asp use down

5 pts.
AS/400 ASP
AS/400 performance
bring asp usage down.. how can i view the journal files and detached them....
Related Questions

Answer Wiki

Thanks. We'll let you know when a new response is added.

After you detatch the receivers you will want to save them
Then you can delete them — actually you can delete them without saving them but that’s not a good idea.

I like to use Disk Space Tasks to determine where to start when I need to clean up a system.
You might as well start with the libraries, files, etc. that take up the most space.

The Disk Space Tasks menu provides the option for collecting disk space information to help show how storage is being used on your system. After collecting the information, you can specify what information to include in a report and then print the report.


1. Collect disk space information:
Set up for weekly collection. Allows for On-The-Fly reports.
I Usually set this up to run Saturday evening at about 19:00.

You can also start this immediately by selecting 1=Date/time then entering *CURRENT for the date and time. This will take some time (Maybe hours) and will take up some additional space to collect the data so don’t do this if you are already over say 95 to 98%.

Once the data has been collected you can print the library report.
It generally has enough information to get you started.

2. Print disk space information:
Type of Report: Library
Include information about objects in libraries: “Y”
Size of smallest library: 99,000

The report will start with a summary then show the library details further down.
I make note in the summary of the % taken up by the libraries, directories, folders, temporary space or anything thats not normal. Then I’ll go down to the list libraries and their files to decide what action to take. Sometimes this will be reorganizing files in the databases, deleting test databases, image catalogs, spool files, etc.


Discuss This Question: 7  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • TheHeck
    You might want to check some other things as well. How about files with large numbers of deleted records (any files GT 10% should be reorgainzed). Are you "reusing deleted records" where you can??? How about clearing out any unnessary spool files in either user output queues or in QEZJOBLOG or QEZDEBUG???
    165 pointsBadges:
  • Yorkshireman
    Ho Hum "Disk is getting full, man the dlete pumps" Hoe often have we heard that one, everyone. The great thing is that iSeries just keeps on and on and on packing stuff away. What other machine would let you store 10 Gb of data on a 4Gb disk? Oh yes, Microsoft finally stole the idea, years later. Anyway As suggested, start with DSPOUTQ and investigate any OUTQ where there are a large number of objects. Ancient joblogs or reports all mean that the job creating them remains on the system, so do some deletes. There are a few good 'mass delete' utilities to remove prints 'older than' on a mass basis. Then turn your attention to libraries. DSPOBJD *ALL objects to an outfile, then query the outfile into size sequence, and go for the big numbers again. Remove redundant objects, test copies of stuff in forgotten libraries. DSPOBJD for *LIB objects, and use the size as a guide. - It is representative, not definitive, but adequate for this task. Again, find who owns the library ( 'created by' userid) and go quiz them about what the object is doing. and, when your disk is back below the magic 82 % - don't stop! ! Every site I've worked on (including my own little domestic AS/400, always stops housekeeping as soon as the disk use is back down. It's the big objects that give quick wins, but the devil is in the 2,370 objects which are using 500 bytes each, or are 'empty files' - every object has a minimum space overhead, and consumes system resource just existing at all.
    6,085 pointsBadges:
  • Nordan
    Have you run RTVDSKINF (collert data) and command and PRTDSKINF (generate a report)? You can use both to check where "heavy" objects are. You can also perform your own queries ussing QAEZDISK file (output of RTVDSKINF).
    435 pointsBadges:
  • mcl
    Yes, to all of the above.. I'll add this - With the system in a restricted state, run the RCLSTG command. You can also run the RCLSPLSTG DAYS(*NONE) command, especially if you deleted lots of spooled files. Regards Mike
    2,740 pointsBadges:
  • Gambitt7
    2 Cents worth - Check for traces; easiest way is via SST, option 3.
    160 pointsBadges:
  • WoodEngineer
    Perhaps someone already mentioned this . . . try GO CLEANUP and check your setup at option 1. Then be sure cleanup is scheduled to run on a regular basis. If you are running performance tools check library QPFRDATA for objects like these: Object Type Size QPMJ04T002 *DTAQ 17850368 QPMJ08T002 *DTAQ 17850368 QPMJ09T002 *DTAQ 17850368 We typically delete any that are older than 30 days. So far that has not caused any problems. At nearly 18Mb each, these data queues can add up pretty quickly.
    8,225 pointsBadges:
  • pdraebel
    If you did not automatically run the CLEANUP issue command STRCLNUP. Also include this in your startup program so cleanup will run automatically even after IPL. Check journal receivers on the system WRKJRNRCV *ALL/*ALL. Some could be very old and if you reinstalled your system some of the Chains of receivers could be broken in which case system maintenace procedures will not clean them up automatically. Peter
    7,545 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: