Re: Production AS/400 ASP size

1. Is ASP usage still growing? If so you need to find the job that's
taking up the space. It may be temporary space and if so it would be freed
up when the job ends. From a WRKACTJOB sort the list by IO or CPU and loot
at the ones with big numbers. If you have WRKSYSACT you can use it to see
which jobs are doing lots of IO. The point being that if ASP usage is
growing faster than it should, you might have a runaway job. Typically
ending that job "fixes" things.

2. I've seen some interactive jobs get caught in a loop where the
connection to the device drops, the job fails, it creates a job log spool
file, and it tries again. It fails again, and the cycle continues until
the job has created the max allowed number of spool files. I'm looking at
you, JDE World. Anyway, for these you can purge the spool files. I used
to use Navigator to do so. If you do purge a ton of spool files consider
running RCLSPLSTG afterwards.

3. Beyond that, there should be info in the archives about doing general
system cleanup. For instance, if you have time you can do a RTVDSKINF (can
run for hours in the background; suggest running overnight) followed by
PRTDSKINF (fast) to look at the non-IFS side of things. You can also do
RTVDIRINF but again it's slow and you have to be selective about which
directories you look at.

On Wed, Aug 1, 2012 at 1:42 PM, John Mathew <johnmathew400@xxxxxxxxx> wrote:

Hi All,

My ASP size has increased to 90%. Is there any way to decrease my ASP
size to 80 or 75.

I searched in google the information I found is delete old query and old
files which are not used for a long time.

is there any other way to reduced my ASP. As it is very urgent.


Can some one please guide me or send some pdf or steps.

Thanks in Advance.

Regards,
John
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.