expertsit
asked on
% system ASP used
1) I'm application developer on as/400 have no idea about system
administrator job. I have questions our As/400 test server saw % %
system ASP used 93.9898 . Our system admin. left the company last
week. I'm trying to figure it out what I need to do get this % down on
test server.
2) We are planning to upgrade our old machine (810) to 510 next weekend. Any idea? What we need to keep in mind to prevent any problem ?
Please advise
Thank you so much in advance
administrator job. I have questions our As/400 test server saw % %
system ASP used 93.9898 . Our system admin. left the company last
week. I'm trying to figure it out what I need to do get this % down on
test server.
2) We are planning to upgrade our old machine (810) to 510 next weekend. Any idea? What we need to keep in mind to prevent any problem ?
Please advise
Thank you so much in advance
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Some of this duplicates Tom's comments, but here goes.
Retrieving the disk and directory information is a good idea. Hunt down the largest objects in the reports to get the most space back the fastest.
WRKJRNRCV *ALL gives the list of journal receivers on the system, where a lot of space can be wasted.
How much total disk is on the system? The auxiliary storage threshold used to default to 90%, but with today's large disk pools, per cent used can climb higher than 90 without imminent threat of the system halting when it reaches 100. For example, on a 1 Terabyte system, 10 per cent of space free is likely more than enough working storage.
From a performance point of view, the arm busy level is more important than the actual amount of space used. Performance is related to how active the data is, not much of it there is. A lot of history data that is rarely accessed will take a long time to affect performance.
For the 810 to 510 upgrade, make sure a full system save is done beforehand:
GO SAVE, then option 21
Make sure you understand what hardware changes are happening. Will there be a load source migration? Will disk protection be stopped and restarted? At any rate, the full system save should be done or some other recovery strategy be in place, in case things go horribly wrong.
Barry
As for the 810-to-510 upgrade, simple personal experience makes me strongly recommend that you not upgrade OS/400 version at the same time you do the hardware upgrade if at all possible. Do OS/400 upgrade separate from the hardware. Bring your current system up to a release of OS/400 that's supported on the new hardware first. THEN migrate that to the new hardware. (We just went through a couple nightmares around that in the past couple weeks.)
It isn't always possible, but it can be very well worth it if you can do it.
Tom
It isn't always possible, but it can be very well worth it if you can do it.
Tom
the simpet answer is by more disks.
What you can check are the following librarues:
QRPLOBJ - these are tempory objects kept by the system after compiles etc.
check for save files
WRKF then f4
select all and allusr then file type savf
Back them up and delete them.
You can aslo check for deleted records in files and reorganise them.
delete old spool files.
These are not going to eat into the 93% and the system works best at under 70%.
Dave