System Save / Clean up / reorg?

0 pts.
Tags:
AS/400
Backup & recovery
DataCenter
Because of the holidays, we're needing to do some maintenance on our AS400 in a much smaller window then we are used to, Normally, we can set aside close to a 24 hour window on a Sunday when we need to do any maintenance that requires taking our AS400 offline, but, this evening, we're limited to about a 6 hour window. Our service provider has warned us to expect up to a 3 hour window for the work that we're having done, but we also need to do a full system save before taking the system offline, which could add another 3 hours to the process. To prepare for the work tonight, I'm doing some last min clean up of our system, and deleting a lot of records out of our test, and dev systems, as well as cleaning up some redundant/unneeded records in our live environment. My question is, as far as speeding up the save, will simply deleting the records speed things up, or will I also need to run a reorg to compact the files? I think that the save will only save active records, and will trim out all of the deleted records, but, I didn't want to make an assumption that could cost us a half hour of our 6 hour window. thanks, Kevin
ASKED: December 21, 2006  12:40 PM
UPDATED: December 27, 2009  10:51 PM

Answer Wiki

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

Just doing the save won’t free up the space or save you time. The SAV* commands do save deleted records. I would do a DSPOBJD of all files in selected libraries and then a DSPFD against those files to find the percentage of deleted records. If it is more than 30% then a reorg should be considered. Anything less won’t buy you much.

But you could do this to save time.
Tonmorrow during normal working hours you can do a SAVLIB *IBM using SAVWHLACT. and a SAV of just the QIBM folder as these don’t require a restricted state

Then instead of a full save later just do GO SAVE option 23 to save user data which will get everything else. That will save a couple hours at least.

In fact a full save once a month and user saves the rest of the time should work as the IBM libraries really only change during OS and PTF upgrades. But still do it at least once a month.

================================================================

A couple things might do more to speed up full system saves than anything else.

First, the number of individual objects can be reduced. Nowadays, the largest part of perhaps most systems is held in the /root file system. Reducing deleted records often has little noticeable effect overall because the number of database files is small compared to the number of streamfiles. Cleaning up /root can be a more valuable way to spend your time.

Second, your authority scheme should minimize private authorities. One way to judge if your authorities are getting out of line is to run SAVSECDTA to a savefile. This can be done without restricted state, but should be scheduled for times when the system is otherwise quiet. If it’s done for a benchmark, you want minimal contention.

Then, if you’re concerned about how long that one item takes, you could run PRTPRFINT SELECT(*PCTFULL) to see where authorities are distributed. Pay attention to any profiles with higher percentages. If it’s a smooth distribution, see how you might start removing private authorities from many profiles and/or many objects. Investigate whether primary group authority might be used. Investigate whether authorities can be moved away from individuals into group profiles. Control at library/directory levels before object levels if private authorities are used. (That might have larger impact if you have database files with many members. Each member duplicates the authorities of the file object, even source files.)

None of that should be taken to mean that deleted records make no difference. But if they’re a significant issue, they probably ought to be handled through elements such as REUSEDLT(), proper file sizing and normal database management. That will give much better ROI for your time than trying cleanup before full-system or user-library saves.

Tom

Discuss This Question: 3  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.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • MODMOD
    thanks for the reply, We do a full sys save every 3 weeks, and nightly changed objects, but, any time we open the box up to replace hardware, we like to have a fresh save from right before. Normally we do the job over the weekend, and I have a lot more time to work with, so the full save isn't a problem, but today, it is :/ I went ahead and did reorgs as a just in case, I normally do anything with more then 1% up to about .5M records, and about 10% for larger files when I do reorgs, and I run those on about a monthly bases (some files more often), so, the only place I had to speed things up was by nuking several gig of test/dev data off the drives. hopefully I bought myself 30 min or so. thanks again.
    0 pointsBadges:
    report
  • JDWWms
    You could also consider doing a save of the test libraries using the *FREE ahead of time. Since those libraries probably are not being used all of the time. The *FREE option leaves the objects on the system but clears the data. This is good becuase it keeps the private authorities but free up space. Then after the maintaince restore the libraries. The only other thing I can thing of is write your own program to do the full save. It is really only four save commands with a restricted state to start and resart at the end: ENDSBS *ALL *IMMED SAVSYS SAVLIB *NONSYS SAVDLO SAV At the end you can do either STRSBS QCTL which is what IBM does or do a PWRDWNSYS *IMMED RESTART(*YES) which would be better. But the save time part is on the SAVLIB *NONSYS, you can omit up to 300 libraries on the command. You could omit all of your Test libraries and save them separately when you have time.
    0 pointsBadges:
    report
  • JDWWms
    You could also consider doing a save of the test libraries using the *FREE ahead of time. Since those libraries probably are not being used all of the time. The *FREE option leaves the objects on the system but clears the data. This is good becuase it keeps the private authorities but free up space. Then after the maintaince restore the libraries. The only other thing I can thing of is write your own program to do the full save. It is really only four save commands with a restricted state to start and resart at the end: ENDSBS *ALL *IMMED SAVSYS SAVLIB *NONSYS SAVDLO SAV At the end you can do either STRSBS QCTL which is what IBM does or do a PWRDWNSYS *IMMED RESTART(*YES) which would be better. But the save time part is on the SAVLIB *NONSYS, you can omit up to 300 libraries on the command. You could omit all of your Test libraries and save them separately when you have time.
    0 pointsBadges:
    report

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.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

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

Following